This paper presents a study called collaborative-adversarial pair (CAP) programming which is an alternative to pair programming\r\n(PP). Its objective is to exploit the advantages of pair programming while at the same time downplaying its disadvantages. Unlike\r\ntraditional pairs, where two people work together in all the phases of software development, CAPs start by designing together;\r\nsplitting into independent test construction and code implementation roles; then joining again for testing. An empirical study was\r\nconducted in fall 2008 and in spring 2009 with twenty-six computer science and software engineering senior and graduate students\r\nat Auburn University. The subjects were randomly divided into two groups (CAP/experimental group and PP/control group). The\r\nsubjects used Eclipse and JUnit to perform three programming tasks with different degrees of complexity. The results of this\r\nexperiment point in favor of CAP development methodology and do not support the claim that pair programming in general\r\nreduces the software development duration, overall software development cost or increases the program quality or correctness.
Loading....